@mor39a Rather than putting scripts directly into the YAML file, I prefer creating a .github/scripts/ directory, placing the executable scripts there, and then calling them from the workflow.

Basically, GitHub Actions can't even be run until they are merged. So, I think we should merge it once it looks good enough and then create follow-up PRs to make adjustments as needed.

@mor39a Rather than putting scripts directly into the YAML file, I prefer creating a .github/scripts/ directory, placing the executable scripts there, and then calling them from the workflow.

Ok, I'll separate them then.

Basically, GitHub Actions can't even be run until they are merged. So, I think we should merge it once it looks good enough and then create follow-up PRs to make adjustments as needed.

I don't recommend implementing features without testing them first. I was planning to run them in a test repository.

We could also set it up to add a “potential-duplicate” label. What do you think, @Kyome22?

await github.rest.issues.addLabels({
  owner: owner,
  repo: repo,
  issue_number: issue.number,
  labels: ['potential-duplicate']
});

I don't recommend implementing features without testing them first. I was planning to run them in a test repository.

Of course, if it's possible to set up a test repository and experiment there, that would be even better.

We could also set it up to add a “potential-duplicate” label. What do you think, @Kyome22?

await github.rest.issues.addLabels({
  owner: owner,
  repo: repo,
  issue_number: issue.number,
  labels: ['potential-duplicate']
});

Adding labels sounds like a great idea. I'm on board with that.